This topic covers troubleshooting tips for PrizmDoc. Note that this topic does not cover issues related to custom web tier implementations.
The following section contains basic troubleshooting steps limited to the PrizmDoc Server itself.
Note that "OS" will be your version of Linux. The health of the services will be displayed.
System Has Limited Resources:
The system resources for a machine running PrizmDoc are described in Sizing Servers > PrizmDoc Server. Please note that PrizmDoc will require at least a few gigabytes free while running and no conversions are taking place. If your system has PrizmDoc installed and idles with 1-2GB free RAM, then the services will run into stability issues.The cache is corrupted or inaccessible:
A common problem is not running or installing PrizmDoc Server as the root user, which is a requirement for running PrizmDoc on a Linux server. Correcting this will solve permission related issues while accessing the cache. To clear a potentially corrupted cache manually, use the following steps:
- Run #/usr/share/prizm/Scripts/pccis.sh stop
- Delete the contents of: /usr/share/prizm/cache/
- Start up PrizmDoc Server: #/usr/share/prizm/Scripts/pccis.sh start
Copy Code################### Prizm Content Connect Configuration ########################
############################### Licensing ######################################
license.solutionName: MySolution
license.key: 2.0.E6Ao...Copy and send your full key to Accusoft Support.